Log Messages Settings

The KAS IDEClosed"Integrated development environment" An integrated development environment is a type of computer software that assists computer programmers in developing software. IDEs normally consist of a source code editor, a compiler and/or interpreter, build-automation tools, and a debugger manages all messages according to the two following gates:

Configuration Settings

Configuration of the Log Messages

Figure 3-9: Configuration of the Local and Controller log messages

Call out# Description

Each log source can be set with its own notification level.

It is possible to get a maximum of log details for the selected source without getting a flood of irrelevant messages from the other sources by controlling the level of each source. See What are the sources of the log messages?, What are the log message levels?, and How do I choose the appropriate level for a log?.

You can set or reset all the sliders with the same level value

Logs can be recorded on the local machine as circular files.

Note that on the controller, the recording of the logs is enabled by default. For more details, see About Local Log File Settings.
Source Apply to...
IDE Win32 applications: the KAS IDE and the KAS RuntimeClosedIn computer science, runtime (or run-time) describes the operation of a computer program, the duration of its execution, from beginning to termination (compare compile time). Within KAS, runtime also refers to the virtual machine that manage the program written in a computer language while it is running Server (also called the KAS Runtime Front-endClosedIn software design, the front-end is the part of a software system that interacts directly with the user)
Controller For the KAS Runtime items: Drivers, IOEngine, SinopEngine...
EtherCAT For all kinds of EtherCATClosed***EtherCAT is an open, high-performance Ethernet-based fieldbus system. The development goal of EtherCAT was to apply Ethernet to automation applications which require short data update times (also called cycle times) with low communication jitter (for synchronization purposes) and low hardware costs items: Motion bus, I/Os
Drive Messages from AKD drive
PLC For application engineers to create custom log within the PLCClosed"Programmable Logic Controller" A Programmable Logic Controller, PLC, or Programmable Controller is a digital computer used for automation of industrial processes, such as control of machinery on factory assembly lines. Used to synchronize the flow of inputs from (physical) sensors and events with the flow of outputs to actuators and events programs (similar to printf)
Motion Messages coming from the Motion engines: PLCopenClosedA vendor -and product- independent worldwide association active in Industrial Control and aiming at standardizing PLC file formats based on XML, Pipe network or VM
System For common API and libraries. Also includes messages issued from the operating system.

Level

Icon

Description
CRITICAL Application crashes or becomes unstable. Data is corrupted. At that point, the application behavior can be unpredictable.
ERROR The application does not behave as expected but the processes remain stable.
WARNING System is stable but the KAS IDE warns that an unexpected event can occur. This is the default logging level.
You can ignore this log.
INFO Information status of the current process.
You can ignore this log.
DEBUG Any information logged for development purpose.
You can ignore this log.

Each message has one of the following levels, with importance in ascending order:
DEBUG > INFO > WARNING > ERROR > CRITICAL

Log files are a group of small files where all the last logs are recorded. Each log is recorded as a separated line.


  • You can import the log files into Microsoft Excel using drag-and-drop.

Field Description
Enabled The Log File Settings has to be enabled to record all the logs.
Log size

To prevent any overflow, you can define the maximum size on disk dedicated to the group of local log files. The minimum size is 1MB, the maximum log size is 2MB. At most, the system will store 20 files. When a new file is created, an old one is deleted, maintaining the 20 file threshold.

In the example below, the size on disk is limited to 100 KBytes (see call out ).

Note that the number of rows can vary for each file, depending on what is in the backlog when KAS creates the log files.
Log Directory The Log Files are stored in this directory. Each KAS IDE instance has a unique log directory, defined by the process identification number. You can access the local log files for this specific instance of the KAS IDE, by clicking this link to open the directory location in the file explorer. For more information see Where are the log files stored?
Log name

You can define the filename prefix to be used on the local machine.(on the controller, the filename prefix is: controller logs).

The suffix to create the complete filename contains a timestampClosedA timestamp is a sequence of characters, denoting the date and/or time at which a certain event occurred with the following format: - day MMM DD HHhMMmSS YYYY nn


  • The Log name change is applied immediately. The name used by the next IDE instance is determined by the last IDE instance.

When a level is set for a source, only messages with the same or higher importance are recorded. In other words, drag the level control slider Up to reduce the verbosity, Down to increase it.
When the configuration leads to lower verbosity, the treatment during the filtering is quicker.

For example, if a source is set to WARNING, then all messages with levels WARNING, ERROR and CRITICAL are recorded (DEBUG and INFO messages are discarded).
In other words, DEBUG is the most verbose, whereas ERROR is the less verbose.


  • Critical messages are always recorded (as a consequence, the Critical level is not visible on the slider).

  • For the local machine (IDE), the Log files are located in the following location:

    C:\Users\(user name)\AppData\Local\Kollmorgen\KAS\Astrolabe\logs\IDE\(process ID)

  • For the controller, the Log files are located under:

    C:\Users\(user name)\AppData\Local\Kollmorgen\KAS\Sinope Simulator\Application\logs

  • The AKD PDMM or PCMM logs are accessed via the web server page by browsing to:

    KAS Application > Log Data.


  • AKD PDMM/PCMM generated logs may be configured through the webpage. See PDMM and PCMM Log Files for more information on those controllers' logs.

Filtering

You can narrow the list of recorded messages by specifying a filter. The filter is applied on all the strings displayed on each row of the table widget (i.e Time, Source, Level and Message).

The drop-down menu gives access to some predefined filters, which can also be edited.

Filtering the Messages

Figure 3-10: Filtering the Messages

For example, filtering with Warning NOT error means that only the lines including the word "warning" but not the word "error" are listed.

The following rules apply when you work with filters:

  • You can combine several strings by including one of the three following Boolean operands:
  • OR
  • AND
  • NOT (or use the exclamation mark "!")
  • Several keywords separated with spaces are considered as an exact string
  • Filtering is not case sensitive

Filtering the Messages - Example

Figure 3-11: Filtering the Messages - Example


  • Warning! When you apply the filter, all the currently recorded messages are parsed and displayed if they match the filter. But all the upcoming recorded messages are added as new rows at the end of the table widget with no filtering.

If you select a message in the table, the scrolling is stopped.
All the upcoming recorded messages are added at the end of the list, but your selected message always remains in the same place (you have to scroll down to make the most recent messages visible).

If you select the last row of the table (shortcut: Alt+Page Down), the scrolling is active.
The last recorded message is always selected and visible at the bottom of the table.